Multi-Household Support

ABSTRACT

Embodiments are provided for enabling a user to control multiple media playback systems with a single mobile device. The mobile device may connect with a first or second media playback system based on receiving a first or second household identifier (HHID), respectively. If the mobile device receives both the first and second HHIDs, the mobile device may connect with either the first or second media playback system based on a priority of the two systems. If neither the first nor second HHIDs are received by the mobile device, a user may be prompted to add a third media playback system if the mobile device receives a third HHID. The user interface of the mobile device may receive an input to connect the mobile device to the third media playback system, and a connection may be established between the mobile device and the third media playback system.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 120 to, and is acontinuation of, U.S. patent application Ser. No. 15/942,818, filed onApr. 2, 2018, entitled “Multi-Household Support,” the contents of whichare incorporated by reference herein in their entirety.

U.S. patent application Ser. No. 15/942,818 claims priority under 35U.S.C. § 120 to, and is a continuation of, U.S. patent application Ser.No. 14/039,615, filed on Sep. 27, 2013, entitled “Multi-HouseholdSupport,” and issued as U.S. Pat. No. 9,933,920 on Apr. 3, 2018, thecontents of which are incorporated by reference herein in theirentirety.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and, more particularly, tomethods, systems, products, features, services, and other items directedto media playback or some aspect thereof.

BACKGROUND

Digital music has become readily available due in part to thedevelopment of consumer level technology that has allowed people tolisten to digital music on a personal audio device. The consumer'sincreasing preference for digital audio has also resulted in theintegration of personal audio devices into PDAs, cellular phones, andother mobile devices. The portability of these mobile devices hasenabled people to take the music listening experience with them andoutside of the home. People have become able to consume digital music,like digital music files or even Internet radio, in the home through theuse of their computer or similar devices. Now there are many differentways to consume digital music, in addition to other digital contentincluding digital video and photos, stimulated in many ways byhigh-speed Internet access at home, mobile broadband Internet access,and the consumer's hunger for digital media.

Until recently, options for accessing and listening to digital audio inan out-loud setting were severely limited. In 2005, Sonos offered forsale its first digital audio system that enabled people to, among manyother things, access virtually unlimited sources of audio via one ormore networked connected zone players, dynamically group or ungroup zoneplayers upon command, wirelessly send the audio over a local networkamongst zone players, and play the digital audio out loud acrossmultiple zone players in synchrony. The Sonos system can be controlledby software applications running on network capable mobile devices andcomputers.

Given the insatiable appetite of consumers towards digital media, therecontinues to be a need to develop consumer technology thatrevolutionizes the way people access and consume digital media.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologymay be better understood with regard to the following description,appended claims, and accompanying drawings where:

FIG. 1 shows an example configuration in which certain embodiments maybe practiced;

FIG. 2A shows an illustration of an example zone player having abuilt-in amplifier and transducers;

FIG. 2B shows an illustration of an example zone player having abuilt-in amplifier and connected to external speakers;

FIG. 2C shows an illustration of an example zone player connected to anA/V receiver and speakers;

FIG. 3 shows an illustration of an example controller;

FIG. 4 shows an internal functional block diagram of an example zoneplayer;

FIG. 5 shows an internal functional block diagram of an examplecontroller;

FIG. 6 shows an example playback queue configuration for a mediaplayback system;

FIG. 7 shows an example ad-hoc playback network;

FIG. 8 shows a system including a plurality of networks including acloud-based network and at least one local playback network;

FIG. 9A shows an example flow diagram for connecting a mobile device toa media playback system;

FIG. 9B shows an example flow diagram for connecting to a mobile deviceto an additional media playback system;

FIG. 10A shows an example user interface for establishing a connectionbetween a mobile device and a media playback system; and

FIGS. 10B-10C show a series of example user interfaces.

In addition, the drawings are for the purpose of illustrating exampleembodiments, but it is understood that the inventions are not limited tothe arrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

Embodiments described herein may involve enabling a user to controlmultiple media playback systems with a single mobile device. In onescenario, a user may have a first media playback system at his or herresidence and a second media playback system at his or her place ofwork. In another scenario, a user may have a first media playback systemat his or her residence and the user's friend may have a second mediaplayback system at their residence. In yet another scenario, a user mayhave multiple media playback systems at his or her residence. In eachscenario, the present disclosure describes a method and correspondingsystem that enables the user to control the first media playback systemand the second media playback system with a single mobile device.

In one example, a mobile device may be registered with a first mediaplayback system having a first household identifier (HHID) and themobile device may also be registered with a second media playback systemhaving a second HHID. When a user launches a controller softwareapplication, the mobile device may send a multicast search message tosearch for an HHID corresponding to a media playback system. The mobiledevice may connect with the first or second media playback system basedon receiving the first or second HHID, respectively. Once connected, theuser may control either the first or second media playback system usingthe mobile device. If the mobile device receives both the first andsecond HHIDs, the mobile device may connect with either the first orsecond media playback system based on a priority of the first and secondmedia playback systems. In one example, the priority is determined basedon a location of the mobile device. In another example, the priority isdetermined based on the order in which each HHID is received by themobile device.

If the user launches the controller application on the mobile device andneither the first nor second HHIDs are received by the mobile device,the user may be prompted to add a third media playback system if themobile device receives a third HHID. In response to the prompt, the userinterface of the mobile device may receive an input to connect themobile device to the third media playback system, and a connection maybe established between the mobile device and the third media playbacksystem.

A list of registered households may be stored in the data storage of themobile device. Further, the user may remove a household from the list ofregistered households. For example, the user interface of the mobiledevice may receive an input to forget the first HHID, and the mobiledevice will no longer connect to the first media playback system. Otherexamples are possible as well.

As indicated above, the present application involves enabling a user tocontrol multiple media playback systems with a single mobile device. Inone aspect, a method is provided. The method involves associating amobile device to a first media playback system having a first HHID andassociating the mobile device to a second media playback system having asecond HHID. The method further involves connecting the mobile device tothe first or second media playback systems based on receiving, by themobile device, the first or second HHID, respectively. The methodfurther involves using the mobile device to send one or more controlcommands to the connected first or second media playback system foraudio playback. The method further involves not connecting the mobiledevice to a third media playback system based on receiving, by themobile device, a third HHID.

In another aspect, a device is provided. The device includes a processorand computer readable medium having stored thereon instructionsexecutable by the processor to perform function. The functions includeassociating a mobile device to a first media playback system having afirst HHID and associating the mobile device to a second media playbacksystem having a second HHID. The functions further include connectingthe mobile device to the first or second media playback systems based onreceiving, by the mobile device, the first or second HHID, respectively.The functions further include using the mobile device to send one ormore control commands to the connected first or second media playbacksystem for audio playback. The functions further include not connectingthe mobile device to a third media playback system based on receiving,by the mobile device, a third HHID.

In yet another aspect, a non-transitory computer readable memory isprovided. The non-transitory computer readable memory has stored thereoninstructions executable by a computing device to cause the computingdevice to perform functions. The functions include associating a mobiledevice to a first media playback system having a first HHID andassociating the mobile device to a second media playback system having asecond HHID. The functions further include connecting the mobile deviceto the first or second media playback systems based on receiving, by themobile device, the first or second HHID, respectively. The functionsfurther include using the mobile device to send one or more controlcommands to the connected first or second media playback system foraudio playback. The functions further include not connecting the mobiledevice to a third media playback system based on receiving, by themobile device, a third HHID.

Other embodiments, as those discussed in the following and others as canbe appreciated by one having ordinary skill in the art are alsopossible.

II. Example Operating Environment

Referring now to the drawings, in which like numerals can refer to likeparts throughout the figures, FIG. 1 shows an example media systemconfiguration 100 in which one or more embodiments disclosed herein canbe practiced or implemented.

By way of illustration, the media system configuration 100 is associatedwith a home having multiple zones, although it should be understood thatthe home could be configured with only one zone. Additionally, one ormore zones can be added to the configuration 100 over time. Each zonemay be assigned by a user to a different room or space, such as, forexample, an office, bathroom, bedroom, kitchen, dining room, familyroom, home theater room, utility or laundry room, and patio. A singlezone might also include multiple rooms or spaces if so configured. Withrespect to FIG. 1, one or more of zone players 102-124 are shown in eachrespective zone. Zone players 102-124, also referred to herein asplayback devices, multimedia units, speakers, players, and so on,provide audio, video, and/or audiovisual output. A controller 130 (e.g.,shown in the kitchen for purposes of this illustration) provides controlto the media system configuration 100. Controller 130 may be fixed to azone, or alternatively, mobile such that it can be moved about thezones. The media system configuration 100 may also include more than onecontroller 130, and additional controllers may be added to the systemover time.

The media system configuration 100 illustrates an example whole housemedia system, though it is understood that the technology describedherein is not limited to, among other things, its particular place ofapplication or to an expansive system like a whole house media system100 of FIG. 1.

a. Example Zone Players

FIGS. 2A, 2B, and 2C show example types of zone players. Zone players200, 202, and 204 of FIGS. 2A, 2B, and 2C, respectively, can correspondto any of the zone players 102-124 of FIG. 1, for example. In someembodiments, audio is reproduced using only a single zone player, suchas by a full-range player. In some embodiments, audio is reproducedusing two or more zone players, such as by using a combination offull-range players or a combination of full-range and specializedplayers. In some embodiments, zone players 200-204 may also be referredto as a “smart speaker,” because they contain processing capabilitiesbeyond the reproduction of audio, more of which is described below.

FIG. 2A illustrates a zone player 200 that includes sound producingequipment 208 capable of reproducing full-range sound. The sound maycome from an audio signal that is received and processed by zone player200 over a wired or wireless data network. Sound producing equipment 208includes one or more built-in amplifiers and one or more acoustictransducers (e.g., speakers). A built-in amplifier is described morebelow with respect to FIG. 4. A speaker or acoustic transducer caninclude, for example, any of a tweeter, a mid-range driver, a low-rangedriver, and a subwoofer. In some embodiments, zone player 200 can bestatically or dynamically configured to play stereophonic audio,monaural audio, or both. In some embodiments, zone player 200 may bedynamically configured to reproduce a subset of full-range sound, suchas when zone player 200 is grouped with other zone players to playstereophonic audio, monaural audio, and/or surround audio or when themedia content received by zone player 200 is less than full-range.

FIG. 2B illustrates zone player 202 that includes a built-in amplifierto power a set of detached speakers 210. A detached speaker can include,for example, any type of loudspeaker. Zone player 202 may be configuredto power one, two, or more separate loudspeakers. Zone player 202 may beconfigured to communicate an audio signal (e.g., right and left channelaudio or more channels depending on its configuration) to the detachedspeakers 210 via a wired path.

FIG. 2C illustrates zone player 204 that does not include a built-inamplifier, but is configured to communicate an audio signal, receivedover a data network, to an audio (or “audio/video”) receiver 214 withbuilt-in amplification.

Referring back to FIG. 1, in some embodiments, one, some, or all of thezone players 102 to 124 can retrieve audio directly from a source. Forexample, a particular zone player in a zone or zone group may beassigned to a playback queue (or “queue”). The playback queue containsinformation corresponding to zero or more audio items for playback bythe associated zone or zone group. The playback queue may be stored inmemory on a zone player or some other designated device. Each itemcontained in the playback queue may comprise a uniform resourceidentifier (URI) or some other identifier that can be used by the zoneplayer(s) to seek out and/or retrieve the audio items from theidentified audio source(s). Depending on the item, the audio sourcemight be found on the Internet (e.g., the cloud), locally from anotherdevice over the data network 128 (described further below), from thecontroller 130, stored on the zone player itself, or from an audiosource communicating directly to the zone player. In some embodiments,the zone player can reproduce the audio itself (e.g., play the audio),send the audio to another zone player for reproduction, or both wherethe audio is reproduced by the zone player as well as one or moreadditional zone players (possibly in synchrony). In some embodiments,the zone player may play a first audio content (or alternatively, maynot play the content at all), while sending a second, different audiocontent to another zone player(s) for reproduction. To the user, eachitem in a playback queue is represented on an interface of a controllerby an element such as a track name, album name, radio station name,playlist, or other some other representation. A user can populate theplayback queue with audio items of interest. The user may also modifyand clear the playback queue, if so desired.

By way of illustration, SONOS, Inc. of Santa Barbara, Calif. presentlyoffers for sale zone players referred to as a “PLAY:5,” “PLAY:3,”“PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present,and/or future zone players can additionally or alternatively be used toimplement the zone players of example embodiments disclosed herein.Additionally, it is understood that a zone player is not limited to theparticular examples illustrated in FIGS. 2A, 2B, and 2C or to the SONOSproduct offerings. For example, a zone player may include a wired orwireless headphone. In yet another example, a zone player might includea sound bar for television. In yet another example, a zone player mayinclude or interact with a docking station for an Apple iPod™ or similardevice.

b. Example Controllers

FIG. 3 illustrates an example wireless controller 300 in docking station302. By way of illustration, controller 300 may correspond tocontrolling device 130 of FIG. 1. Docking station 302, if provided orused, may provide power to the controller 300 and additionally maycharge a battery of controller 300. In some embodiments, controller 300may be provided with a touch screen 304 that allows a user to interactthrough touch with the controller 300, for example, to retrieve andnavigate a playlist of audio items, modify and/or clear the playbackqueue of one or more zone players, control other operations of one ormore zone players, and provide overall control of the systemconfiguration 100. In other embodiments, other input mechanisms such asvoice control may be used to interact with the controller 300. Incertain embodiments, any number of controllers can be used to controlthe system configuration 100. In some embodiments, there may be a limitset on the number of controllers that can control the systemconfiguration 100. The controllers might be wireless like wirelesscontroller 300 or wired to data network 128.

In some embodiments, if more than one controller is used in system 100of FIG. 1, each controller may be coordinated to display common content,and may all be dynamically updated to indicate changes made to thesystem 100 from a single controller. Coordination can occur, forinstance, by a controller periodically requesting a state variabledirectly or indirectly from one or more of the zone players; the statevariable may provide information about system 100, such as current zonegroup configuration, what is playing in one or more zones, volumelevels, and other items of interest. The state variable may be passedaround on data network 128 between zone players (and controllers, if sodesired) as needed or as often as programmed.

In addition, an application running on any network-enabled portabledevice, such as an iPhone™, iPad™, Android™ powered phone or tablet, orany other smart phone or network-enabled device can be used ascontroller 130. An application running on a laptop or desktop personalcomputer (PC) or Mac™ can also be used as controller 130. Suchcontrollers may connect to system 100 through an interface with datanetwork 128, a zone player, a wireless router, or using some otherconfigured connection path. Example controllers offered by Sonos, Inc.of Santa Barbara, Calif. include a “Controller 200,” “SONOS® CONTROL,”“SONOS® Controller for iPhone™,” “SONOS® Controller for iPad™,” “SONOS®Controller for Android™,” “SONOS® Controller for Mac™ or PC.”

c. Example Data Connection

Zone players 102-124 of FIG. 1 are coupled directly or indirectly to adata network, such as data network 128. Controller 130 may also becoupled directly or indirectly to data network 128 or individual zoneplayers. Data network 128 is represented by an octagon in the figure tostand out from other representative components. While data network 128is shown in a single location, it is understood that such a network isdistributed in and around system 100. Particularly, data network 128 canbe a wired network, a wireless network, or a combination of both wiredand wireless networks. In some embodiments, one or more of the zoneplayers 102-124 are wirelessly coupled to data network 128 based on aproprietary mesh network. In some embodiments, one or more of the zoneplayers are coupled to data network 128 using a centralized access pointsuch as a wired or wireless router. In some embodiments, one or more ofthe zone players 102-124 are coupled via a wire to data network 128using Ethernet or similar technology. In addition to the one or morezone players 102-124 connecting to data network 128, data network 128can further allow access to a wide area network, such as the Internet.

In some embodiments, connecting any of the zone players 102-124, or someother connecting device, to a broadband router, can create data network128. Other zone players 102-124 can then be added wired or wirelessly tothe data network 128. For example, a zone player (e.g., any of zoneplayers 102-124) can be added to the system configuration 100 by simplypressing a button on the zone player itself (or perform some otheraction), which enables a connection to be made to data network 128. Thebroadband router can be connected to an Internet Service Provider (ISP),for example. The broadband router can be used to form another datanetwork within the system configuration 100, which can be used in otherapplications (e.g., web surfing). Data network 128 can also be used inother applications, if so programmed. An example, second network mayimplement SONOSNET™ protocol, developed by SONOS, Inc. of Santa Barbara.SONOSNET™ represents a secure, AES-encrypted, peer-to-peer wireless meshnetwork. Alternatively, in certain embodiments, the data network 128 isthe same network, such as a traditional wired or wireless network, usedfor other applications in the household.

d. Example Zone Configurations

A particular zone can contain one or more zone players. For example, thefamily room of FIG. 1 contains two zone players 106 and 108, while thekitchen is shown with one zone player 102. In another example, the hometheater room contains additional zone players to play audio from a 5.1channel or greater audio source (e.g., a movie encoded with 5.1 orgreater audio channels). In some embodiments, one can position a zoneplayer in a room or space and assign the zone player to a new orexisting zone via controller 130. As such, zones may be created,combined with another zone, removed, and given a specific name (e.g.,“Kitchen”), if so desired and programmed to do so with controller 130.Moreover, in some embodiments, zone configurations may be dynamicallychanged even after being configured using controller 130 or some othermechanism.

In some embodiments, a “bonded zone” is a zone that contains two or morezone players, such as the two zone players 106 and 108 in the familyroom, whereby the two zone players 106 and 108 can be configured to playthe same audio source in synchrony. In one example, the two zone players106 and 108 can be paired to play two separate sounds in left and rightchannels, for example. In other words, the stereo effects of a sound canbe reproduced or enhanced through the two zone players 106 and 108, onefor the left sound and the other for the right sound. In another exampletwo or more zone players can be sonically consolidated to form a single,consolidated zone player. A consolidated zone player (though made up ofmultiple, separate devices) can be configured to process and reproducesound differently than an unconsolidated zone player or zone playersthat are paired, because a consolidated zone player has additionalspeaker drivers from which sound can be passed. The consolidated zoneplayer can further be paired with a single zone player or yet anotherconsolidated zone player. Each playback device of a consolidatedplayback device can be set in a consolidated mode, for example.

In certain embodiments, paired zone players (also referred to as “bondedzone players”) can play audio in synchrony with other zone players inthe same or different zones.

According to some embodiments, one can continue to do any of: group,consolidate, and pair zone players, for example, until a desiredconfiguration is complete. The actions of grouping, consolidation, andpairing are preferably performed through a control interface, such asusing controller 130, and not by physically connecting and re-connectingspeaker wire, for example, to individual, discrete speakers to createdifferent configurations. As such, certain embodiments described hereinprovide a more flexible and dynamic platform through which soundreproduction can be offered to the end-user.

e. Example Audio Sources

In some embodiments, each zone can play from the same audio source asanother zone or each zone can play from a different audio source. Forexample, someone can be grilling on the patio and listening to jazzmusic via zone player 124, while someone is preparing food in thekitchen and listening to classical music via zone player 102. Further,someone can be in the office listening to the same jazz music via zoneplayer 110 that is playing on the patio via zone player 124. In someembodiments, the jazz music played via zone players 110 and 124 isplayed in synchrony. Synchronizing playback amongst zones allows for anindividual to pass through zones while seamlessly (or substantiallyseamlessly) listening to the audio. Further, zones can be put into a“party mode” such that all associated zones will play audio insynchrony.

Sources of audio content to be played by zone players 102-124 arenumerous. In some embodiments, audio on a zone player itself may beaccessed and played. In some embodiments, audio on a controller may beaccessed via the data network 128 and played. In some embodiments, musicfrom a personal library stored on a computer or networked-attachedstorage (NAS) may be accessed via the data network 128 and played. Insome embodiments, Internet radio stations, shows, and podcasts may beaccessed via the data network 128 and played. Music or cloud servicesthat let a user stream and/or download music and audio content may beaccessed via the data network 128 and played. Further, music may beobtained from traditional sources, such as a turntable or CD player, viaa line-in connection to a zone player, for example. Audio content mayalso be accessed using a different protocol, such as Airplay™, which isa wireless technology by Apple, Inc., for example. Audio contentreceived from one or more sources can be shared amongst the zone players102 to 124 via data network 128 and/or controller 130. Theabove-disclosed sources of audio content are referred to herein asnetwork-based audio information sources. However, network-based audioinformation sources are not limited thereto.

In some embodiments, the example home theater zone players 116, 118, 120are coupled to an audio information source such as a television 132. Insome examples, the television 132 is used as a source of audio for thehome theater zone players 116, 118, 120, while in other examples audioinformation from the television 132 may be shared with any of the zoneplayers 102-124 in the audio system 100.

III. Example Zone Players

Referring now to FIG. 4, there is shown an example block diagram of azone player 400 in accordance with an embodiment. Zone player 400includes a network interface 402, a processor 408, a memory 410, anaudio processing component 412, one or more modules 414, an audioamplifier 416, and a speaker unit 418 coupled to the audio amplifier416. FIG. 2A shows an example illustration of such a zone player. Othertypes of zone players may not include the speaker unit 418 (e.g., suchas shown in FIG. 2B) or the audio amplifier 416 (e.g., such as shown inFIG. 2C). Further, it is contemplated that the zone player 400 can beintegrated into another component. For example, the zone player 400could be constructed as part of a television, lighting, or some otherdevice for indoor or outdoor use.

In some embodiments, network interface 402 facilitates a data flowbetween zone player 400 and other devices on a data network 128. In someembodiments, in addition to getting audio from another zone player ordevice on data network 128, zone player 400 may access audio directlyfrom the audio source, such as over a wide area network or on the localnetwork. In some embodiments, the network interface 402 can furtherhandle the address part of each packet so that it gets to the rightdestination or intercepts packets destined for the zone player 400.Accordingly, in certain embodiments, each of the packets includes anInternet Protocol (IP)-based source address as well as an IP-baseddestination address.

In some embodiments, network interface 402 can include one or both of awireless interface 404 and a wired interface 406. The wireless interface404, also referred to as a radio frequency (RF) interface, providesnetwork interface functions for the zone player 400 to wirelesslycommunicate with other devices (e.g., other zone player(s), speaker(s),receiver(s), component(s) associated with the data network 128, and soon) in accordance with a communication protocol (e.g., any wirelessstandard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac,802.15, 4G mobile communication standard, and so on). Wireless interface404 may include one or more radios. To receive wireless signals and toprovide the wireless signals to the wireless interface 404 and totransmit wireless signals, the zone player 400 includes one or moreantennas 420. The wired interface 406 provides network interfacefunctions for the zone player 400 to communicate over a wire with otherdevices in accordance with a communication protocol (e.g., IEEE 802.3).In some embodiments, a zone player includes multiple wireless 404interfaces. In some embodiments, a zone player includes multiple wired406 interfaces. In some embodiments, a zone player includes both of theinterfaces 404 and 406. In some embodiments, a zone player 400 includesonly the wireless interface 404 or the wired interface 406.

In some embodiments, the processor 408 is a clock-driven electronicdevice that is configured to process input data according toinstructions stored in memory 410. The memory 410 is data storage thatcan be loaded with one or more software module(s) 414, which can beexecuted by the processor 408 to achieve certain tasks. In theillustrated embodiment, the memory 410 is a tangible machine-readablemedium storing instructions that can be executed by the processor 408.In some embodiments, a task might be for the zone player 400 to retrieveaudio data from another zone player or a device on a network (e.g.,using a uniform resource locator (URL) or some other identifier). Insome embodiments, a task may be for the zone player 400 to send audiodata to another zone player or device on a network. In some embodiments,a task may be for the zone player 400 to synchronize playback of audiowith one or more additional zone players. In some embodiments, a taskmay be to pair the zone player 400 with one or more zone players tocreate a multi-channel audio environment. Additional or alternativetasks can be achieved via the one or more software module(s) 414 and theprocessor 408.

The audio processing component 412 can include one or moredigital-to-analog converters (DAC), an audio preprocessing component, anaudio enhancement component or a digital signal processor, and so on. Insome embodiments, the audio processing component 412 may be part ofprocessor 408. In some embodiments, the audio that is retrieved via thenetwork interface 402 is processed and/or intentionally altered by theaudio processing component 412. Further, the audio processing component412 can produce analog audio signals. The processed analog audio signalsare then provided to the audio amplifier 416 for playback throughspeakers 418. In addition, the audio processing component 412 caninclude circuitry to process analog or digital signals as inputs to playfrom zone player 400, send to another zone player on a network, or bothplay and send to another zone player on the network. An example inputincludes a line-in connection (e.g., an auto-detecting 3.5 mm audioline-in connection).

The audio amplifier 416 is a device(s) that amplifies audio signals to alevel for driving one or more speakers 418. The one or more speakers 418can include an individual transducer (e.g., a “driver”) or a completespeaker system that includes an enclosure including one or more drivers.A particular driver can be a subwoofer (e.g., for low frequencies), amid-range driver (e.g., for middle frequencies), and a tweeter (e.g.,for high frequencies), for example. An enclosure can be sealed orported, for example. Each transducer may be driven by its own individualamplifier.

A commercial example, presently known as the PLAY:5™, is a zone playerwith a built-in amplifier and speakers that is capable of retrievingaudio directly from the source, such as on the Internet or on the localnetwork, for example. In particular, the PLAY:5™ is a five-amp,five-driver speaker system that includes two tweeters, two mid-rangedrivers, and one woofer. When playing audio content via the PLAY:5, theleft audio data of a track is sent out of the left tweeter and leftmid-range driver, the right audio data of a track is sent out of theright tweeter and the right mid-range driver, and mono bass is sent outof the subwoofer. Further, both mid-range drivers and both tweeters havethe same equalization (or substantially the same equalization). That is,they are both sent the same frequencies but from different channels ofaudio. Audio from Internet radio stations, online music and videoservices, downloaded music, analog audio inputs, television, DVD, and soon, can be played from the PLAY:5™.

IV. Example Controller

Referring now to FIG. 5, there is shown an example block diagram forcontroller 500, which can correspond to the controlling device 130 inFIG. 1. Controller 500 can be used to facilitate the control ofmulti-media applications, automation and others in a system. Inparticular, the controller 500 may be configured to facilitate aselection of a plurality of audio sources available on the network andenable control of one or more zone players (e.g., the zone players102-124 in FIG. 1) through a wireless or wired network interface 508.According to one embodiment, the wireless communications is based on anindustry standard (e.g., infrared, radio, wireless standards includingIEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobilecommunication standard, and so on). Further, when a particular audio isbeing accessed via the controller 500 or being played via a zone player,a picture (e.g., album art) or any other data, associated with the audioand/or audio source can be transmitted from a zone player or otherelectronic device to controller 500 for display.

Controller 500 is provided with a screen 502 and an input interface 514that allows a user to interact with the controller 500, for example, tonavigate a playlist of many multimedia items and to control operationsof one or more zone players. The screen 502 on the controller 500 can bean LCD screen, for example. The screen 500 communicates with and iscommanded by a screen driver 504 that is controlled by a microcontroller(e.g., a processor) 506. The memory 510 can be loaded with one or moreapplication modules 512 that can be executed by the microcontroller 506with or without a user input via the user interface 514 to achievecertain tasks. In some embodiments, an application module 512 isconfigured to facilitate grouping a number of selected zone players intoa zone group to facilitate synchronized playback amongst the zoneplayers in the zone group. In some embodiments, an application module512 is configured to control the audio sounds (e.g., volume) of the zoneplayers in a zone group. In operation, when the microcontroller 506executes one or more of the application modules 512, the screen driver504 generates control signals to drive the screen 502 to display anapplication specific user interface accordingly.

The controller 500 includes a network interface 508 that facilitateswired or wireless communication with a zone player. In some embodiments,the commands such as volume control and audio playback synchronizationare sent via the network interface 508. In some embodiments, a savedzone group configuration is transmitted between a zone player and acontroller via the network interface 508. The controller 500 can controlone or more zone players, such as 102-124 of FIG. 1. There can be morethan one controller for a particular system, and each controller mayshare common information with another controller, or retrieve the commoninformation from a zone player, if such a zone player storesconfiguration data (e.g., such as a state variable). Further, acontroller can be integrated into a zone player.

It should be noted that other network-enabled devices such as aniPhone™, iPad™ or any other smart phone or network-enabled device (e.g.,a networked computer such as a PC or Mac™) can also be used as acontroller to interact or control zone players in a particularenvironment. In some embodiments, a software application or upgrade canbe downloaded onto a network-enabled device to perform the functionsdescribed herein.

In certain embodiments, a user can create a zone group (also referred toas a bonded zone) including at least two zone players from thecontroller 500. The zone players in the zone group can play audio in asynchronized fashion, such that all of the zone players in the zonegroup playback an identical audio source or a list of identical audiosources in a synchronized manner such that no (or substantially no)audible delays or hiccups are to be heard. Similarly, in someembodiments, when a user increases the audio volume of the group fromthe controller 500, the signals or data of increasing the audio volumefor the group are sent to one of the zone players and causes other zoneplayers in the group to be increased together in volume.

A user via the controller 500 can group zone players into a zone groupby activating a “Link Zones” or “Add Zone” soft button, or de-grouping azone group by activating an “Unlink Zones” or “Drop Zone” button. Forexample, one mechanism for ‘joining’ zone players together for audioplayback is to link a number of zone players together to form a group.To link a number of zone players together, a user can manually link eachzone player or room one after the other. For example, assume that thereis a multi-zone system that includes the following zones: Bathroom,Bedroom, Den, Dining Room, Family Room, and Foyer. In certainembodiments, a user can link any number of the six zone players, forexample, by starting with a single zone and then manually linking eachzone to that zone.

In certain embodiments, a set of zones can be dynamically linkedtogether using a command to create a zone scene or theme (subsequent tofirst creating the zone scene). For instance, a “Morning” zone scenecommand can link the Bedroom, Office, and Kitchen zones together in oneaction. Without this single command, the user would manually andindividually link each zone. The single command may include a mouseclick, a double mouse click, a button press, a gesture, or some otherprogrammed or learned action. Other kinds of zone scenes can beprogrammed or learned by the system over time.

In certain embodiments, a zone scene can be triggered based on time(e.g., an alarm clock function). For instance, a zone scene can be setto apply at 8:00 am. The system can link appropriate zonesautomatically, set specific music to play, and then stop the music aftera defined duration and revert the zones to their prior configuration.Although any particular zone can be triggered to an “On” or “Off” statebased on time, for example, a zone scene enables any zone(s) linked tothe scene to play a predefined audio (e.g., a favorable song, apredefined playlist) at a specific time and/or for a specific duration.If, for any reason, the scheduled music failed to be played (e.g., anempty playlist, no connection to a share, failed Universal Plug and Play(UPnP), no Internet connection for an Internet Radio station, and soon), a backup buzzer can be programmed to sound. The buzzer can includea sound file that is stored in a zone player, for example.

V. Playback Queue

As discussed above, in some embodiments, a zone player may be assignedto a playback queue identifying zero or more media items for playback bythe zone player. The media items identified in a playback queue may berepresented to the user via an interface on a controller. For instance,the representation may show the user (or users if more than onecontroller is connected to the system) how the zone player is traversingthe playback queue, such as by highlighting the “now playing” item,graying out the previously played item(s), highlighting the to-be-playeditem(s), and so on.

In some embodiments, a single zone player is assigned to a playbackqueue. For example, zone player 114 in the bathroom of FIG. 1 may belinked or assigned to a “Bathroom” playback queue. In an embodiment, the“Bathroom” playback queue might have been established by the system as aresult of the user naming the zone player 114 to the bathroom. As such,contents populated and identified in the “Bathroom” playback queue canbe played via the zone player 114 (the bathroom zone).

In some embodiments, a zone or zone group is assigned to a playbackqueue. For example, zone players 106 and 108 in the family room of FIG.1 may be linked or assigned to a “Family room” playback queue. Inanother example, if family room and dining room zones were grouped, thenthe new group would be linked or assigned to a family room+dining roomplayback queue. In some embodiments, the family room+dining roomplayback queue would be established based upon the creation of thegroup. In some embodiments, upon establishment of the new group, thefamily room+dining room playback queue can automatically include thecontents of one (or both) of the playback queues associated with eitherthe family room or dining room or both. In one instance, if the userstarted with the family room and added the dining room, then thecontents of the family room playback queue would become the contents ofthe family room+dining room playback queue. In another instance, if theuser started with the family room and added the dining room, then thefamily room playback queue would be renamed to the family room+diningroom playback queue. If the new group was “ungrouped,” then the familyroom+dining room playback queue may be removed from the system and/orrenamed to one of the zones (e.g., renamed to “family room” or “diningroom”). After ungrouping, each of the family room and the dining roomwill be assigned to a separate playback queue. One or more of the zoneplayers in the zone or zone group may store in memory the associatedplayback queue.

As such, when zones or zone groups are “grouped” or “ungrouped”dynamically by the user via a controller, the system will, in someembodiments, establish or remove/rename playback queues respectively, aseach zone or zone group is to be assigned to a playback queue. In otherwords, the playback queue operates as a container that can be populatedwith media items for playback by the assigned zone. In some embodiments,the media items identified in a playback queue can be manipulated (e.g.,re-arranged, added to, deleted from, and so on).

By way of illustration, FIG. 6 shows an example network 600 for mediacontent playback. As shown, the example network 600 includes examplezone players 612 and 614, example audio sources 662 and 664, and examplemedia items 620. The example media items 620 may include playlist 622,music track 624, favorite Internet radio station 626, playlists 628 and630, and album 632. In one embodiment, the zone players 612 and 614 maybe any of the zone players shown in FIGS. 1, 2, and 4. For instance,zone players 612 and 614 may be the zone players 106 and 108 in theFamily Room.

In one example, the example audio sources 662 and 664, and example mediaitems 620 may be partially stored on a cloud network, discussed morebelow in connection to FIG. 8. In some cases, the portions of the audiosources 662, 664, and example media items 620 may be stored locally onone or both of the zone players 612 and 614. In one embodiment, playlist622, favorite Internet radio station 626, and playlist 630 may be storedlocally, and music track 624, playlist 628, and album 632 may be storedon the cloud network.

Each of the example media items 620 may be a list of media itemsplayable by a zone player(s). In one embodiment, the example media itemsmay be a collection of links or pointers (i.e., URI) to the underlyingdata for media items that are stored elsewhere, such as the audiosources 662 and 664. In another embodiment, the media items may includepointers to media content stored on the local zone player, another zoneplayer over a local network, or a controller device connected to thelocal network.

As shown, the example network 600 may also include an example queue 602associated with the zone player 612, and an example queue 604 associatedwith the zone player 614. Queue 606 may be associated with a group, whenin existence, comprising zone players 612 and 614. Queue 606 mightcomprise a new queue or exist as a renamed version of queue 602 or 604.In some embodiments, in a group, the zone players 612 and 614 would beassigned to queue 606 and queue 602 and 604 would not be available atthat time. In some embodiments, when the group is no longer inexistence, queue 606 is no longer available. Each zone player and eachcombination of zone players in a network of zone players, such as thoseshown in FIG. 1 or that of example zone players 612, 614, and examplecombination 616, may be uniquely assigned to a corresponding playbackqueue.

A playback queue, such as playback queues 602-606, may includeidentification of media content to be played by the corresponding zoneplayer or combination of zone players. As such, media items added to theplayback queue are to be played by the corresponding zone player orcombination of zone players. The zone player may be configured to playitems in the queue according to a specific order (such as an order inwhich the items were added), in a random order, or in some other order.

The playback queue may include a combination of playlists and othermedia items added to the queue. In one embodiment, the items in playbackqueue 602 to be played by the zone player 612 may include items from theaudio sources 662, 664, or any of the media items 622-632. The playbackqueue 602 may also include items stored locally on the zone player 612,or items accessible from the zone player 614. For instance, the playbackqueue 602 may include Internet radio 626 and album 632 items from audiosource 662, and items stored on the zone player 612.

When a media item is added to the queue via an interface of acontroller, a link to the item may be added to the queue. In a case ofadding a playlist to the queue, links to the media items in the playlistmay be provided to the queue. For example, the playback queue 602 mayinclude pointers from the Internet radio 626 and album 632, pointers toitems on the audio source 662, and pointers to items on the zone player612. In another case, a link to the playlist, for example, rather than alink to the media items in the playlist may be provided to the queue,and the zone player or combination of zone players may play the mediaitems in the playlist by accessing the media items via the playlist. Forexample, the album 632 may include pointers to items stored on audiosource 662. Rather than adding links to the items on audio source 662, alink to the album 632 may be added to the playback queue 602, such thatthe zone player 612 may play the items on the audio source 662 byaccessing the items via pointers in the album 632.

In some cases, contents as they exist at a point in time within aplayback queue may be stored as a playlist, and subsequently added tothe same queue later or added to another queue. For example, contents ofthe playback queue 602, at a particular point in time, may be saved as aplaylist, stored locally on the zone player 612 and/or on the cloudnetwork. The saved playlist may then be added to playback queue 604 tobe played by zone player 614.

VI. Example Ad-Hoc Network

Particular examples are now provided in connection with FIG. 7 todescribe, for purposes of illustration, certain embodiments to provideand facilitate connection to a playback network. FIG. 7 shows that thereare three zone players 702, 704 and 706 and a controller 708 that form anetwork branch that is also referred to as an Ad-Hoc network 710. Thenetwork 710 may be wireless, wired, or a combination of wired andwireless technologies. In general, an Ad-Hoc (or “spontaneous”) networkis a local area network or other small network in which there isgenerally no one access point for all traffic. With an establishedAd-Hoc network 710, the devices 702, 704, 706 and 708 can allcommunicate with each other in a “peer-to-peer” style of communication,for example. Furthermore, devices may join and/or leave from the network710, and the network 710 will automatically reconfigure itself withoutneeding the user to reconfigure the network 710. While an Ad-Hoc networkis referenced in FIG. 7, it is understood that a playback network may bebased on a type of network that is completely or partially differentfrom an Ad-Hoc network.

Using the Ad-Hoc network 710, the devices 702, 704, 706, and 708 canshare or exchange one or more audio sources and be dynamically grouped(or ungrouped) to play the same or different audio sources. For example,the devices 702 and 704 are grouped to playback one piece of music, andat the same time, the device 706 plays back another piece of music. Inother words, the devices 702, 704, 706 and 708, as shown in FIG. 7, forma HOUSEHOLD that distributes audio and/or reproduces sound. As usedherein, the term HOUSEHOLD (provided in uppercase letters todisambiguate from the user's domicile) is used to represent a collectionof networked devices that are cooperating to provide an application orservice. An instance of a HOUSEHOLD is identified with a household 710(or household identifier), though a HOUSEHOLD may be identified with adifferent area or place.

In certain embodiments, a household identifier (HHID) is a short stringor an identifier that is computer-generated to help ensure that it isunique. Accordingly, the network 710 can be characterized by a uniqueHHID and a unique set of configuration variables or parameters, such aschannels (e.g., respective frequency bands), service set identifier(SSID) (a sequence of alphanumeric characters as a name of a wirelessnetwork), and WEP keys (wired equivalent privacy) or other securitykeys. In certain embodiments, SSID is set to be the same as HHID.

In certain embodiments, each HOUSEHOLD includes two types of networknodes: a control point (CP) and a zone player (ZP). The control pointcontrols an overall network setup process and sequencing, including anautomatic generation of required network parameters (e.g., securitykeys). In an embodiment, the CP also provides the user with a HOUSEHOLDconfiguration user interface. The CP function can be provided by acomputer running a CP application module, or by a handheld controller(e.g., the controller 308) also running a CP application module, forexample. The zone player is any other device on the network that isplaced to participate in the automatic configuration process. The ZP, asa notation used herein, includes the controller 308 or a computingdevice, for example. In some embodiments, the functionality, or certainparts of the functionality, in both the CP and the ZP are combined at asingle node (e.g., a ZP contains a CP or vice-versa).

In certain embodiments, configuration of a HOUSEHOLD involves multipleCPs and ZPs that rendezvous and establish a known configuration suchthat they can use a standard networking protocol (e.g., IP over Wired orWireless Ethernet) for communication. In an embodiment, two types ofnetworks/protocols are employed: Ethernet 802.3 and Wireless 802.11g.Interconnections between a CP and a ZP can use either of thenetworks/protocols. A device in the system as a member of a HOUSEHOLDcan connect to both networks simultaneously.

In an environment that has both networks in use, it is assumed that atleast one device in a system is connected to both as a bridging device,thus providing bridging services between wired/wireless networks forothers. The zone player 706 in FIG. 7 is shown to be connected to bothnetworks, for example. The connectivity to the network 712 is based onEthernet and/or Wireless, while the connectivity to other devices 702,704 and 708 is based on Wireless and Ethernet if so desired.

It is understood, however, that in some embodiments each zone player706, 704, 702 may access the Internet when retrieving media from thecloud (e.g., the Internet) via the bridging device. For example, zoneplayer 702 may contain a uniform resource locator (URL) that specifiesan address to a particular audio track in the cloud. Using the URL, thezone player 702 may retrieve the audio track from the cloud, andultimately play the audio out of one or more zone players.

VII. Another Example System Configuration

FIG. 8 shows a system 800 including a plurality of interconnectednetworks including a cloud-based network and at least one local playbacknetwork. A local playback network includes a plurality of playbackdevices or players, though it is understood that the playback networkmay contain only one playback device. In certain embodiments, eachplayer has an ability to retrieve its content for playback. Control andcontent retrieval can be distributed or centralized, for example. Inputcan include streaming content provider input, third party applicationinput, mobile device input, user input, and/or other playback networkinput into the cloud for local distribution and playback.

As illustrated by the example system 800 of FIG. 8, a plurality ofcontent providers 820-850 can be connected to one or more local playbacknetworks 860-870 via a cloud and/or other network 810. Using the cloud810, a multimedia audio system server 820 (e.g., Sonos™), a mobiledevice 830, a third party application 840, a content provider 850 and soon can provide multimedia content (requested or otherwise) to localplayback networks 860, 870. Within each local playback network 860, 870,a controller 862, 872 and a playback device 864, 874 can be used toplayback audio content.

VIII. Example Multi-Household Support for Multiple Media PlaybackSystems

As discussed above, embodiments described herein may involve enabling auser to control multiple media playback systems with a single mobiledevice. FIG. 9A shows an example flow diagram for connecting a mobiledevice to multiple media playback systems, in accordance with at leastsome embodiments described herein. Method 900 shown in FIG. 9A presentsan embodiment of a method that could be used in the environments 100,600, 700 and 800 with the systems 200, 202, 204, 300, 400, and 500 forexample, in communication with one or more devices, such as thoseillustrated in FIGS. 2-5. Method 900 may include one or more operations,functions, or actions as illustrated by one or more of blocks 902-908.Although the blocks are illustrated in sequential order, these blocksmay also be performed in parallel, and/or in a different order thanthose described herein. Also, the various blocks may be combined intofewer blocks, divided into additional blocks, and/or removed based uponthe desired implementation.

In addition, for the method 900 and other processes and methodsdisclosed herein, the flowchart shows functionality and operation of onepossible implementation of present embodiments. In this regard, eachblock may represent a module, a segment, or a portion of program code,which includes one or more instructions executable by a processor forimplementing specific logical functions or steps in the process. Theprogram code may be stored on any type of computer readable medium, forexample, such as a storage device including a disk or hard drive. Thecomputer readable medium may include non-transitory computer readablemedium, for example, such as computer-readable media that stores datafor short periods of time like register memory, processor cache andRandom Access Memory (RAM). The computer readable medium may alsoinclude non-transitory media, such as secondary or persistent long termstorage, like read only memory (ROM), optical or magnetic disks,compact-disc read only memory (CD-ROM), for example. The computerreadable media may also be any other volatile or non-volatile storagesystems. The computer readable medium may be considered a computerreadable storage medium, for example, or a tangible storage device. Inaddition, for the method 800 and other processes and methods disclosedherein, each block in FIG. 9A may represent circuitry that is wired toperform the specific logical functions in the process.

At block 902, the method 900 involves associating a mobile device to afirst media playback system having a first HHID and associating themobile device to a second media playback system having a second HHID. Asused herein, a mobile device includes any network-enabled portabledevice, such as an IPHONE™, IPAD™, ANDROID™ powered phone or tablet, orany other smart phone or network-enabled device.

As discussed above, the term HOUSEHOLD (provided in uppercase letters todisambiguate from the user's domicile) is used to represent a collectionof networked media playback devices that are cooperating to provide anapplication or service. An instance of a HOUSEHOLD is identified with anHHID. In certain embodiments, an HHID is a short string or an identifierthat is computer-generated to help ensure that it is unique.Accordingly, a media playback system can be characterized by a uniqueHHID and a unique set of configuration variables or parameters, such aschannels (e.g., respective frequency bands), service set identifier(SSID) (a sequence of alphanumeric characters as a name of a wirelessnetwork), and WEP keys (wired equivalent privacy) or other securitykeys. In certain embodiments, SSID is set to be the same as HHID. Otherexamples are possible as well. Additional description of the use ofHHIDs and of the association of various devices to HOUSEHOLDs can befound in U.S. Pat. No. 8,326,951, also assigned to SONOS, Inc., thecontents of which are incorporated by reference herein.

The mobile device may include a software application configured tooperate as a controller for one or more media playback systems. Throughthe controller software application, the mobile device may send a searchmessage to search for an HHID corresponding to a media playback system.The search message may be a multicast message sent over a local areanetwork. In addition, the search message may specifically identifyeither the first HHID or the second HHID. As an alternative, the searchmessage may simply request any HHID. In response to the search message,one or more devices on the network may respond to the search message byproviding a HHID associated with the device(s).

In another example embodiment, the controller device does not send out asearch message. Instead, one or more devices on the network mayperiodically broadcast the HHID associated with the device(s). Anapplication on the controller device may listen for the HHID broadcastto identify an available HOUSEHOLD.

The mobile device may detect the first HHID corresponding to the firstmedia playback system, and responsively, the user interface of themobile device may display on a display screen or alternate userinterface an invitation to connect the mobile device to the first mediaplayback system. The mobile device may receive an input to connect themobile device to the first media playback system, and a connectionbetween the mobile device and the first media playback system may beestablished and the HHID may be registered to the mobile device.Further, the mobile device may detect the second HHID corresponding to asecond media playback system, and may also establish a connectionbetween the mobile device and the second media playback system andregister the HHID to the mobile device using the just described method.The mobile device may store a list of registered HHIDs in the datastorage of the mobile device, including the first HHID and the secondHHID.

At block 904, the method 900 involves connecting the mobile device tothe first or second media playback system based on receiving, by themobile device, the first or second HHID, respectively. As discussedabove, the mobile device may send a multicast search message to searchfor an HHID corresponding to a media playback system (or simply listenfor a message containing an HHID). In one example, if the mobile devicereceives the first HHID in response to the search message, then themobile device will automatically connect to the first media playbacksystem. Similarly, if the mobile device receives the second HHID inresponse to the search message, then the mobile device willautomatically connect to the second media playback system.

In one embodiment, the mobile device may determine its location and usethe determined location as a further basis for connecting the mobiledevice to the first or second media playback system. The mobile devicemay determine its location through a Global Positioning System (GPS)receiver in the mobile device, as an example. In another example, themobile device may determine its location based on the IP address of thenetwork used to connect with the media playback system. In yet anotherexample, the mobile device may determine its location based on thedetection of a wireless network (e.g., by detecting the SSID). Otherexamples of determining the location of the mobile device are possibleas well.

In another embodiment, the mobile device may receive both the first andsecond HHIDs. This may occur, for example, in a situation where a userhas multiple media playback systems in the user's residence, or wherethe mobile device is detecting a first media playback system. If themobile device receives both the first and second HHIDs, the mobiledevice may display an indication on the user interface that both thefirst and second media systems are available to join, and allow the userto select, via the user interface of the mobile device, either the firstor second media playback system for connection.

In another example, if the mobile device receives both the first andsecond HHIDs, the mobile device may automatically select either thefirst or second media playback system for connection based on a priorityof the first and second media playback systems. In one example, thepriority is based on the order in which the HHID is received by themobile device. For example, if the first HHID is received by the mobiledevice before the second HHID, the mobile device will select the firstmedia playback system for connection. In another example, the priorityis determined based on the location of the mobile device. The first timea user connects the mobile device to a particular media playback system,the mobile device may determine the location of the media playbacksystem and store that information in the data storage of the mobiledevice. As discussed above, the location may be determined based oninformation from a GPS receiver in the mobile device, based on the IPaddress of the network used to connect with the media playback system,or through some other means. When a mobile device receives both thefirst and second HHIDs, the mobile device may determine its location andcompare its current location to the stored locations of the first andsecond media playback systems. If the current location of the mobiledevice is closer to the location of the first media playback system, themobile device may select the first media playback system for connection.

In yet another example, when the mobile device receives both the firstand second HHIDs, a geo-fence may be used to determine the priority. Ageo-fence is a virtual region specified in relation to a correspondinggeographical region. For example, a geo-fence that encircles at leastpart of a building can be specified with a latitude and longitude pairand a given radius. In other examples, polygons, such as triangles orrectangles, or other shapes can be used to specify a geo-fence. In oneembodiment, a first geo-fence may be associated with the first mediaplayback system, and a second geo-fence may be associated with a secondmedia playback system.

The mobile device may determine entry within a particular geo-fence bydetermining its current location, determining a difference D between thecurrent location and the center point (a, b) of the geo-fence, andcomparing the difference D to the radius R of geo-fence. For example,let (x, y) be the current position of the mobile device. The differenceD between the mobile device's current position and the center point ofthe geo-fence is determined as D=√{square root over ((x−a)²+(y−b)²)}.The difference D can be compared to the radius R of the geo-fence. If Dis less than R, then the mobile device is within the boundary of thegeo-fence. Similarly, in another example, the difference D can bedetermined as D=(x−a)²+(y−b)². This difference can be compared with thesquare of the radius of the geo-fence (R²). If D is less than R², themobile device is within the boundary of the geo-fence. There areadditional mechanisms by which the mobile device may determine whetherit is within the geo-fence boundaries as well (e.g., maintaining a listof acceptable coordinates, etc.).

If a mobile device determines it is within the boundary of the firstgeo-fence associated with the first media playback system, the mobilemay select the first media playback system for connection. Further, whena mobile device enters the first geo-fence, the mobile device may beconfigured to launch the controller software application. In addition,when a mobile device leaves the first geo-fence, the mobile device maybe configured to shut down the controller software application. Shuttingdown the controller software application when the mobile device leavesthe first geo-fence may help conserve the battery life of the mobiledevice. Similar approaches may be used when the mobile device enters andexits a second geo-fence associated with the second media playbacksystem.

At block 906, the method 900 involves using the mobile device to sendone or more control commands to the connected first or second mediaplayback system for audio playback. The commands may include volumecontrol, audio playback synchronization between one or more zoneplayers, selection of a playlist or particular song, or other commandsto provide overall control of the system configuration. The commands maybe received on a controller interface, which may be a softwareapplication provided on the mobile device. The controller interface mayinclude a touch screen that allows a user to interact through touch withthe mobile device. In other embodiments, other input mechanisms such asvoice control may be used to interact with the mobile device.

At block 908, the method 900 involves not connecting the mobile deviceto a third media playback system based on receiving, by the mobiledevice, a third HHID. As discussed above, the mobile device may send amulticast search message to search for an HHID corresponding to a mediaplayback system. The mobile device may determine that it did not receiveany of its registered HHIDs (e.g., the first HHID or the second HHID).However, the mobile device may detect a third HHID corresponding to athird media playback system. The mobile device will not automaticallyconnect the mobile device to the third media playback system uponreceiving the third HHID. Instead, the mobile device can connect to thethird media playback system using the method described in FIG. 9B.

FIG. 9B shows an example flow diagram for connecting to a mobile deviceto an additional media playback system, which is a continuation of themethod 900 shown in FIG. 9A. Method 950 shown in FIG. 9B presents anembodiment of a method that could be used in the environments 100, 600,700 and 800 with the systems 200, 202, 204, 300, 400, and 500 forexample, in communication with one or more devices, such as thoseillustrated in FIGS. 2-5. Method 950 may include one or more operations,functions, or actions as illustrated by one or more of blocks 952-956.Although the blocks are illustrated in sequential order, these blocksmay also be performed in parallel, and/or in a different order thanthose described herein. Also, the various blocks may be combined intofewer blocks, divided into additional blocks, and/or removed based uponthe desired implementation.

At block 952, the method 950 may involve providing for display on a userinterface of the mobile device an invitation to connect the mobiledevice to the third media playback system. The invitation to connect tothe mobile device to the third media playback system may be displayed inresponse to the mobile device receiving the third HHID.

At block 954, the method 950 may involve receiving at the user interfaceof the mobile device an input to connect the mobile device to the thirdmedia playback system. As discussed above, the user interface mayinclude a touch screen that allows a user to interact through touch withthe mobile device. In other embodiments, other input mechanisms such asvoice control may be used to interact with the mobile device. Inaddition, if the mobile device connects to the third playback system,the mobile device may communicate with the third playback system inorder to establish a geo-fence associated with the third playbacksystem. For example, the mobile device may provide the third playbacksystem with a set of coordinates reflecting the mobile device's currentposition, as well as a radius associated with the geo-fence.Alternatively, the third playback system may indicate that it isassociated with an existing geo-fence, and provide those coordinates tothe mobile device.

At block 956, the method 950 may involve establishing a connectionbetween the mobile device and the third media playback system andregistering the third media playback system to the mobile device. Oncethe connection is established, the mobile device may send one or morecommands to the connected third media playback system for audioplayback. As discussed above, the commands may include volume control,audio playback synchronization between one or more zone players,selection of a playlist or particular song, or other commands to provideoverall control of the system configuration. The third media playbacksystem may be added to the list of registered HHIDs in the data storageof the mobile device.

The controller software application may allow a threshold number ofregistered HHIDs to avoid maxing out memory. For example, the controllersoftware application may support up to 100 HHIDs corresponding to 100different media playback systems. After the threshold is met, thecontroller software application may be configured to remove the leastrecently used HHID from the memory of the mobile device.

IX. Illustrative Mobile Device Functionality

FIG. 10A shows an example user interface for establishing a connectionbetween a mobile device and a media playback system. As described above,the mobile device may send a multicast search message to search for anHHID corresponding to a media playback system. The mobile device maydetermine that it did not receive any of its registered HHIDs (e.g., thefirst HHID or the second HHID). In response, the mobile device maydisplay an invitation to connect the mobile device to another mediaplayback system.

FIG. 10A shows the example interface 1000 of the mobile device when themobile device did not receive any of its registered HHIDs in response tosending a multicast search message (or listening for messages thatinclude a HHID). The user may select the “Add Another Sonos System” icon1002 to connect with another media playback system. The additional mediaplayback system may be added to the list of registered HHIDs in the datastorage of the mobile device.

FIGS. 10B-10C show a series of example user interfaces. FIG. 10B showsan example settings interface 1050 of the mobile device when the mobiledevice receives multiple HHIDs in response to sending the multicastsearch message. Similar to the icon discussed above in relation to FIG.10A, the user may select the “Add Another Sonos System” icon 1052 toconnect with a media playback system that is not registered to themobile device. If two registered HHIDs are received by the mobiledevice, the user may select the “Select Sonos System” icon 1054 toselect the media playback system with which to connect.

Further, the user may select the “Forget Current Sonos System” icon 1056to remove a media playback system from the list of registered systems.FIG. 10C shows an example settings interface 1050 of the mobile devicewhen the user selects the “Forget Current Sonos System” icon 1056. Theuser may confirm his or her desire to remove a media playback systemfrom the list of registered systems by selecting the “Forget” icon 1058.Other example methods, interactions and interfaces may also be possible.

X. Conclusion

The descriptions above disclose various example systems, methods,apparatus, and articles of manufacture including, among othercomponents, firmware and/or software executed on hardware. However, suchexamples are merely illustrative and should not be considered aslimiting. For example, it is contemplated that any or all of thesefirmware, hardware, and/or software components can be embodiedexclusively in hardware, exclusively in software, exclusively infirmware, or in any combination of hardware, software, and/or firmware.Accordingly, while the following describes example systems, methods,apparatus, and/or articles of manufacture, the examples provided are notthe only way(s) to implement such systems, methods, apparatus, and/orarticles of manufacture.

As indicated above, the present application involves enabling a user tocontrol multiple media playback systems with a single mobile device. Inone aspect, a method is provided. The method involves associating amobile device to a first media playback system having a first HHID andassociating the mobile device to a second media playback system having asecond HHID. The method further involves connecting the mobile device tothe first or second media playback systems based on receiving, by themobile device, the first or second HHID, respectively. The methodfurther involves using the mobile device to send one or more controlcommands to the connected first or second media playback system foraudio playback. The method further involves not connecting the mobiledevice to a third media playback system based on receiving, by themobile device, a third HHID.

In another aspect, a device is provided. The device includes a processorand computer readable medium having stored thereon instructionsexecutable by the processor to perform function. The functions includeassociating a mobile device to a first media playback system having afirst HHID and associating the mobile device to a second media playbacksystem having a second HHID. The functions further include connectingthe mobile device to the first or second media playback systems based onreceiving, by the mobile device, the first or second HHID, respectively.The functions further include using the mobile device to send one ormore control commands to the connected first or second media playbacksystem for audio playback. The functions further include not connectingthe mobile device to a third media playback system based on receiving,by the mobile device, a third HHID.

In yet another aspect, a non-transitory computer readable memory isprovided. The non-transitory computer readable memory has stored thereoninstructions executable by a computing device to cause the computingdevice to perform functions. The functions include associating a mobiledevice to a first media playback system having a first HHID andassociating the mobile device to a second media playback system having asecond HHID. The functions further include connecting the mobile deviceto the first or second media playback systems based on receiving, by themobile device, the first or second HHID, respectively. The functionsfurther include using the mobile device to send one or more controlcommands to the connected first or second media playback system foraudio playback. The functions further include not connecting the mobiledevice to a third media playback system based on receiving, by themobile device, a third HHID.

Additionally, references herein to “embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment can be included in at least one example embodiment of theinvention. The appearances of this phrase in various places in thespecification are not necessarily all referring to the same embodiment,nor are separate or alternative embodiments mutually exclusive of otherembodiments. As such, the embodiments described herein, explicitly andimplicitly understood by one skilled in the art, can be combined withother embodiments.

The specification is presented largely in terms of illustrativeenvironments, systems, procedures, steps, logic blocks, processing, andother symbolic representations that directly or indirectly resemble theoperations of data processing devices coupled to networks. These processdescriptions and representations are typically used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art. Numerous specific details are set forth to provide athorough understanding of the present disclosure. However, it isunderstood to those skilled in the art that certain embodiments of thepresent disclosure can be practiced without certain, specific details.In other instances, well known methods, procedures, components, andcircuitry have not been described in detail to avoid unnecessarilyobscuring aspects of the embodiments. Accordingly, the scope of thepresent disclosure is defined by the appended claims rather than theforgoing description of embodiments.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible mediumsuch as a memory, DVD, CD, Blu-ray, and so on, storing the softwareand/or firmware.

1. A system comprising a computing device, the computing devicecomprising: a network interface; at least one processor; and at leastone non-transitory computer-readable medium comprising programinstructions that are executable by the at least one processor such thatthe computing device is configured to perform functions comprising:while the computing device is connected to a first local area networkvia the network interface, detecting, via the network interface, a firstmedia playback system comprising first playback devices that areconnected to the first local area network, wherein the first local areanetwork has one or more first network parameters identifying the firstlocal area network; causing, via a control application, display of anindication of the first media playback system in a graphical userinterface of the control application; after receiving input dataindicating a selection of at least one first playback device, causing,via the network interface, the at least one first playback device toplay back first audio content; while the computing device is connectedto a second local area network and disconnected from the first localarea network, detecting, via the network interface, a second mediaplayback system comprising second playback devices that are connected tothe second local area network, wherein the second local area network hasone or more second network parameters identifying the second local areanetwork; causing, via the control application, display of an indicationof the second media playback system in the graphical user interface ofthe control application; and after receiving input data indicating aselection of at least one second playback device, causing, via thenetwork interface, the at least one second playback device to play backsecond audio content.
 2. The system of claim 1, wherein the receivedinput data indicating the selection of at least one second playbackdevice comprises particular input data indicating the selection of asynchrony group comprising a particular second playback device and atleast one additional playback device, and wherein causing the at leastone second playback device to play back the second audio contentcomprises causing the particular second playback device and the at leastone additional playback device to play back the second audio content insynchrony.
 3. The system of claim 2, wherein the received input dataindicating the selection of at least one first playback device comprisesparticular input data indicating the selection of a bonded zonecomprising a set of first playback devices, and wherein causing the atleast one first playback device to play back the first audio contentcomprises causing the set of first playback devices to play back therespective channels of the first audio content.
 4. The system of claim2, wherein the functions further comprise: after ungrouping theparticular second playback device and the at least one additionalplayback device, causing, via the control application, display ofanother indication of the second media playback system in the graphicaluser interface of the control application.
 5. The system of claim 4,wherein the functions further comprise: after receiving input dataindicating a selection of the particular second playback device,causing, via the network interface, the particular second playbackdevice to play back third audio content.
 6. The system of claim 1,wherein detecting the first media playback system comprising the firstplayback devices that are connected to the first local area networkcomprises: sending, via the network interface, a multicast message onthe first local area network; and receiving, via the network interface,one or more responses to the multicast message from the at least onefirst playback device.
 7. The system of claim 1, wherein the one or morefirst network parameters identifying the first local area networkcomprise a first service set identifier of the first local area network,and wherein the second one or more network parameters identifying thesecond local area network comprise a second service set identifier ofthe second local area network.
 8. The system of claim 7, wherein thefirst service set identifier is configured as a first householdidentifier that uniquely identifies the first media playback systemamong a plurality of media playback systems, and wherein the secondservice set identifier is configured as a second household identifierthat uniquely identifies the second media playback system among theplurality of media playback systems.
 9. A tangible, non-transitorycomputer-readable medium comprising program instructions that areexecutable by at least one processor such that a computing device isconfigured to perform functions comprising: while the computing deviceis connected to a first local area network via a network interface,detecting, via the network interface, a first media playback systemcomprising first playback devices that are connected to the first localarea network, wherein the first local area network has one or more firstnetwork parameters identifying the first local area network; causing,via a control application, display of an indication of the first mediaplayback system in a graphical user interface of the controlapplication; after receiving input data indicating a selection of atleast one first playback device, causing, via the network interface, theat least one first playback device to play back first audio content;while the computing device is connected to a second local area networkand disconnected from the first local area network, detecting, via thenetwork interface, a second media playback system comprising secondplayback devices that are connected to the second local area network,wherein the second local area network has one or more second networkparameters identifying the second local area network; causing, via thecontrol application, display of an indication of the second mediaplayback system in the graphical user interface of the controlapplication; and after receiving input data indicating a selection of atleast one second playback device, causing, via the network interface,the at least one second playback device to play back second audiocontent.
 10. The tangible, non-transitory computer-readable medium ofclaim 9, wherein the received input data indicating the selection of atleast one second playback device comprises particular input dataindicating the selection of a synchrony group comprising a particularsecond playback device and at least one additional playback device, andwherein causing the at least one second playback device to play back thesecond audio content comprises causing the particular second playbackdevice and the at least one additional playback device to play back thesecond audio content in synchrony.
 11. The tangible, non-transitorycomputer-readable medium of claim 10, wherein the received input dataindicating the selection of at least one first playback device comprisesparticular input data indicating the selection of a bonded zonecomprising a set of first playback devices, and wherein causing the atleast one first playback device to play back the first audio contentcomprises causing the set of first playback devices to play back therespective channels of the first audio content.
 12. The tangible,non-transitory computer-readable medium of claim 10, wherein thefunctions further comprise: after ungrouping the particular secondplayback device and the at least one additional playback device,causing, via the control application, display of another indication ofthe second media playback system in the graphical user interface of thecontrol application.
 13. The tangible, non-transitory computer-readablemedium of claim 12, wherein the functions further comprise: afterreceiving input data indicating a selection of the particular secondplayback device, causing, via the network interface, the particularsecond playback device to play back third audio content.
 14. Thetangible, non-transitory computer-readable medium of claim 9, whereindetecting the first media playback system comprising the first playbackdevices that are connected to the first local area network comprises:sending, via the network interface, a multicast message on the firstlocal area network; and receiving, via the network interface, one ormore responses to the multicast message from the at least one firstplayback device.
 15. The tangible, non-transitory computer-readablemedium of claim 9, wherein the one or more first network parametersidentifying the first local area network comprise a first service setidentifier of the first local area network, and wherein the one or moresecond network parameters identifying the second local area networkcomprise a second service set identifier of the second local areanetwork.
 16. The tangible, non-transitory computer-readable medium ofclaim 15, wherein the first service set identifier is configured as afirst household identifier that uniquely identifies the first mediaplayback system among a plurality of media playback systems, and whereinthe second service set identifier is configured as a second householdidentifier that uniquely identifies the second media playback systemamong the plurality of media playback systems.
 17. A method to beperformed by a computing device, the method comprising: while thecomputing device is connected to a first local area network via anetwork interface, detecting, via the network interface, a first mediaplayback system comprising first playback devices that are connected tothe first local area network, wherein the first local area network hasone or more first network parameters identifying the first local areanetwork; causing, via a control application, display of an indication ofthe first media playback system in a graphical user interface of thecontrol application; after receiving input data indicating a selectionof at least one first playback device, causing, via the networkinterface, the at least one first playback device to play back firstaudio content; while the computing device is connected to a second localarea network and disconnected from the first local area network,detecting, via the network interface, a second media playback systemcomprising second playback devices that are connected to the secondlocal area network, wherein the second local area network has one ormore second network parameters identifying the second local areanetwork; causing, via the control application, display of an indicationof the second media playback system in the graphical user interface ofthe control application; and after receiving input data indicating aselection of at least one second playback device, causing, via thenetwork interface, the at least one second playback device to play backsecond audio content.
 18. The method of claim 17, wherein the receivedinput data indicating the selection of at least one second playbackdevice comprises particular input data indicating the selection of asynchrony group comprising a particular second playback device and atleast one additional playback device, and wherein causing the at leastone second playback device to play back the second audio contentcomprises causing the particular second playback device and the at leastone additional playback device to play back the second audio content insynchrony.
 19. The method of claim 18, further comprising: afterungrouping the particular second playback device and the at least oneadditional playback device, causing, via the control application,display of another indication of the second media playback system in thegraphical user interface of the control application.
 20. The method ofclaim 19, further comprising: after receiving input data indicating aselection of the particular second playback device, causing, via thenetwork interface, the particular second playback device to play backthird audio content.